ci: dogfood semvertag against this repo#5
Merged
Conversation
Auto-tags on push to main when the latest commit is a feat/ merge (minor) or bugfix/hotfix/ merge (patch). The default branch_prefix mapping is `feature/`; this repo uses `feat/` so the workflow overrides SEMVERTAG_BRANCH_PREFIX__MINOR. Tag creation does NOT trigger publish.yml (which fires on GitHub release creation, not tag push) — to publish to PyPI, create a release pointed at the auto-tagged commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Wire semvertag 0.3.0 into this repo's own CI to dogfood the GitHub provider against
api.github.comend-to-end. Tagsmainon every push when afeat/.../bugfix/.../hotfix/...merge warrants a bump; otherwise exits 0 silently..github/workflows/semvertag.ymlbased on the recipe indocs/providers/github.mdSEMVERTAG_BRANCH_PREFIX__MINOR=["feat/"]to match this repo's actual branch convention (the defaultfeature/wouldn't match any of our merges)GITHUB_TOKEN(workflow declarespermissions: contents: write)concurrency: semvertagserializes back-to-back pushes so they don't race the create_tag APIpublish.yml— that still fires on GitHub release creation onlyTest plan
chore/...which doesn't match any bump prefix, so the workflow should run, decide "no bump", and exit 0 without creating a tagfeat/...merge to main should trigger an auto-tag (likely 0.4.0)🤖 Generated with Claude Code